Notes/Domino Fix List
 |  |
| SPR # JCHN5E6H3X | Fixed in 6.0.2; 6.0.1 CF2 release |  |
Product Area: Server Technical Area: Networking & Dialup Platform: Cross Platform
SPR# JCHN5E6H3X - Fixed a router crash with the console error message PANIC: OSVBlockAddr: Bad VBlock handle (0\0). This problem has been fixed in 6.0.2 and 6.0.1 CF2.
Technote Number: 1089513
Problem:
This issue was reported to Lotus Software Quality Engineering and has been
fixed in Domino Release 6.0.1 CF2.
Excerpt from the Lotus Notes and Domino Release 6.0.1 CF2 fix list (available
at http://www.lotus.com/ldd):
Networking & Dialup
SPR# JCHN5E6H3X - Fixed a router crash with the console error message PANIC:
OSVBlockAddr: Bad VBlock handle (0\0).
Unix stack trace:
###################################
###### thread 28/32 :: router, pid=17480, lwp=28, tid=27 ######
###################################
[1] ff29b4dc _read (125800, 0, 400, 484, 5400, 540d) + c
[2] fd9d87cc fatal_error (b, f9110260, f910ffa8, 0, 0, 0) + 1a8
[3] ff0bb82c __sighndlr (b, f9110260, f910ffa8, fd9d8624, f9111e14, f9111e04)
+ c
[4] ff0b8504 sigacthandler (b, f9111d70, 0, 0, 0, ff0ce000) + 708
[5] --- called from signal handler with signal 11 (SIGSEGV) ---
[6] ff0b9790 __sigprocmask (ff0bbf68, 0, 0, f9111d70, ff0ce000, 0) + 8
[7] ff0ae14c _sigon (f9111d70, ff0d5938, b, f9110444, f9111d70, 2) + d0
[8] ff0b118c _thrp_kill (0, 1b, b, ff0ce000, 1b, fd9f593c) + f8
[9] ff24b738 raise (b, 0, fc34882c, 4c00, 40000000, 0) + 40
[10] fda0fb14 Panic (f9110ad0, 1, 26800, 269d4, fc34882c, fedef638) + 184
[11] fda35c7c OSVBlockAddr (ff00d42c, f9110b80, 0, 4, f83dc26c, 6) + 98
[12] fe301fe4 GetBuffer (0, f9110ef4, f9110ef0, 6, 4, 1184) + ec
[13] fe329f1c ClientUpdateNoteExtended2 (ff00d42c, ffff, 0, 0, f9110fd8,
255f4) + 3ec
[14] fe329a34 ClientUpdateNoteExtended (0, f9110fe8, 4, 0, 0, f9111060) + 27c
[15] fe329b18 ClientUpdateNote (0, 1b, 4, e6d4c4, f9111140, fed7e9a0) + 38
[16] fe329ac8 ClientNoteUpdate (1b, 4, f9111140, 0, ffff0000, 4) + 10
[17] fdfd64f4 DispatchNoteUpdate (f9111310, 1b, 4, 0, 0, 0) + 370
[18] fdfd5e40 NSFNoteUpdateExtended2 (0, 4, 0, 0, 0, 1b) + 5b4
[19] fdfd577c NSFNoteUpdate (1b, 4, f911140c, f9111410, 2d50000, 2d5) + 1c
[20] fe49d58c MailTransferMessage (0, 1, be41d618, fed7e9a0, 1b, 162) + 51c
[21] 00034cfc TransferToDestinationViaNotes (0, 0, be41caaf, 104, be41c97c,
be41ca80) + c10
[22] 00034058 Transfer (89274, f9111ac4, 0, f9111bd0, 0, f8393aae) + 454
[23] 0003f6a0 TransferThread (0, 3000, 2, 16, 89800, 89800) + 3c8
[24] fd9f73e0 ThreadWrapper (58e8, fc34882c, 5800, 58ec, fc34882c, 58f0) + 124
[25] ff0bb730 _thread_start (0, 0, 0, 0, 0, 0) + 40
On Windows 2000/NT (nRouter):
############################################################
### FATAL THREAD 21/29 [ nRouter:00ce:0118]
### FP=1f8ef0c8, PC=6019581d, SP=1f8eeb5c, stksize=1388
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x6019581d nnotes._Panic@4+237 (1f8ef0e0,0,1e64a4a4,0)
@[ 2] 0x60003e82 nnotes._OSVBlockAddr@8+114 (60c33600,0,0,4)
@[ 3] 0x60174ecf nnotes._GetBuffer@12+111 (2ebc0003,1f8ef414,1f8ef40c,0)
@[ 4] 0x6050b8eb nnotes._ClientUpdateNoteExtended2@56+507 (0,123,4,0)
@[ 5] 0x6050b668 nnotes._ClientUpdateNoteExtended@28+440 (209912ac,123,4,0)
@[ 6] 0x6050b6e3 nnotes._ClientUpdateNote@12+51 (0,123,4,1f8ef50c)
@[ 7] 0x6050b6a2 nnotes._ClientNoteUpdate@8+18 (123,4,0,123)
@[ 8] 0x600e8841 nnotes._DispatchNoteUpdate@28+529 (1,123,4,0)
@[ 9] 0x600e8409 nnotes._NSFNoteUpdateExtended2@20+1065 (1d310000,4,0,0)
@[10] 0x601423eb nnotes._NSFNoteUpdate@8+27 (123,4,8170674,1f8e0000)
@[11] 0x608b0dbd nnotes._MailTransferMessage@16+941
(44423b2,8170002,81709e8,1df)
@[12] 0x0040e2ab nRouter._TransferToDestinationViaNotes@20+2363
(444260,1f8efcdc,44423b2,10)
@[13] 0x0040d90a nRouter._Transfer@32+682 (444260,95c0001,0,1f8efcdc)
@[14] 0x00415f7f nRouter._TransferThread@4+607 (0,3,0,2)
@[15] 0x6011c7a4 nnotes._ThreadWrapper@4+212 (0,2,3,0)
[16] 0x77f04ede KERNEL32.lstrcmpiW+190 More >
Last Modified on 03/03/2010
Go back
|